Summary

Extend the kelos-triage TaskSpawner prompt to handle the full triage lifecycle instead of stopping after kind classification:

• Add priority assessment (task 5) with priority/important-soon, priority/important-longterm, and priority/backlog labels and clear criteria for each level
• Add actor recommendation (task 6) with explicit criteria for actor/kelos vs needs-actor
• Update label management to swap needs-triage → triage-accepted after posting the triage comment
• Update the triage comment format to include Priority and Actor fields with justifications

Before: Triage agent classifies (kind/*) and checks validity, then stops. Maintainer must manually assess priority, assign actor, and update 3-4 labels per issue.

After: Triage agent completes all label operations. Maintainer reviews the triage comment (now includes priority + actor justification) and removes kelos/needs-input to approve — a single operation instead of 5.

This is a prompt-only change to self-development/kelos-triage.yaml. No API, CRD, or controller changes required.

Supersedes #444 (rebased on main with axon→kelos rename applied).

Closes #437

Test plan

• Verify YAML is valid and the promptTemplate parses correctly
• Verify the triage agent correctly applies priority labels on a test issue
• Verify the triage agent correctly assesses actor suitability
• Verify the triage agent swaps needs-triage → triage-accepted
• Verify kelos/needs-input is still applied as the human review gate

🤖 Generated with Claude Code